Submit a BugNeXT report
¬
 
¬  Choose Open from the Submit menu to get a Submit window.   
¬  Use the fields and buttons in the Submit window to complete the report.   ¬  Click Submit to send the report to NeXT via electronic mail.  ¬  Close the window, or click Clear to reuse it. 

¬

If you don't have time to finish a report, you can save it in a file by choosing Save or Save As from the Submit menu.  When you want to finish the report, choose Open from the Submit menu to reload it into the Submit window.  

Here's how to complete the form:

¬	Topic;¬Topic 
	Make your best guess.  If you know only the general topic, it's OK to select a node (like  "Mach" or  "App Support") that is in the left or middle column of the topic browser.  Some of the topics have a brief description that may help you decide if this topic is appropriate for the report in question.

¬	Description;¬Description
	If you can reproduce the problem, please detail the steps.  
	If you cannot reproduce the problem, please say so.

	Describe any of the following that could be relevant:  special fonts, modified hardware, is the machine a server in any way (NFS, NetInfo, database, ...), other apps running at the time of the bug, special daemons, or other situations special to your system.  
	
	Please don't send TIFF files of Alert Panels.  Instead just select, copy, and paste the text of the message into your report.  

	BugNeXT automatically appends current system information at the bottom of the Description, so please run BugNeXT on the same machine that the problem occurred on.  If that isn't possible, edit the information in the Description to reflect the problem situation.
	
	Our team at NeXT requests reports written in English!  

¬	Title;¬Summary
	Type a summary of up to 95 characters.  The summary is important to the people receiving your report, so keep it informative!  If the summary includes filler words such as "bug,"  "problem," "minor,"  or "UI," please reword it to increase its content.  Usually the topic doesn't need to be repeated in the summary.  Here are some examples of bad and good summaries:

	Bad				Good
	Mail crasher		crash when scrolling last message in mailbox
	UI bug in PB		Save enabled when no document open
	Fax bug report	double-click user name should assign fax

¬	Severity;¬Severity
	Select a category from the Severity pop-up menu, assessing the impact of the problem.  Here are the available categories:

	Severity	Meaning
	Suggestion	any ideas for new features
	Annoyance	typos and UI inconsistencies
	Avoidable Bug	problems you can work around
	Unavoidable Bug	problems you can't work around
	App Hang/Crash	causes app to hang or crash
	Logged Out	WindowServer or Workspace quits
	System Hang/Crash	causes system to hang or crash

¬

See also

;SettingPreferences.rtfd;;¬	Set BugNeXT Preferences